Our setup: Quota limits on Database store is 500MB. 1 user needs to copy 1GB from a PST file to his mailbox. So, for this individual user, I increased his mailbox quota to 1.5GB. I then connected his mailbox on my PC, and also opened the source PST file. I started copying the contents of the PST file to his mailbox. But, after copying a bit it stops with the message "The Message Store reached it's maximum size". When I check the mailbox, it's now filled up to 500MB. So the old quota. So somewhere, it doesn't seem to accept the new 1.5GB quoa. This is really weird for me. Anybody an idea?Edit: I'm connected with an Outlook 2007 client, to our Exchange 2007 SP1 RO2 environment. I'm not working in Offline (cached) mode, so no .ost files.Edit 2: from the eventvwr on the Exchange server: The mailbox for /o=Exchange Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=ex070353test has exceeded the maximum mailbox size. This mailbox cannot send or receive messages. Incoming messages to this mailbox are returned to sender. The mailbox owner should be notified about the condition of the mailbox as soon as possible. So, it does seem to have to do with quota. But still makes no sense for me. The way I see it:a) Set Quotas on the mailbox database: 'general' settingb) If you then set a different quato on a user's mailbox, this overwrite the general mailbox database setting.Or am I wrong there, and the (smaller) mailbox database quota takes precedence over the individual user mailbox quota?Thnx

The size limit change probably hasnt taken yet.You can speed that up by restarting the store or wait ( up to 2 hours)You can also change the default cache time.More Info:http://technet.microsoft.com/en-us/library/aa998523.aspx( And check out the links at the bottom as well)Note that indivdual limits take precedence over store limits.

THe information is cached. As Andy states you can speed this up by restarting the services. If you believe you will be doing much of this in the future, and you don't want to disrupt all of your users by restarting services, then I'd recommend shortenting the timeiuts.John

Hi,Yes,I agree with Andy. You can follow the steps in article that Andy gave to change the default cache time. But please note thatif weset this value too low, performance issues may will be occur. Sopleasechange the value back after you solve the issue.Regards,Xiu

Thnx. When I checked next day, the new limit indeed was active. I just asumed that mailbox quota's were active immediately.